2015-06-24 - 16728 - Spec - SNC - .Net app for uploading work order confirmations #SNCProject

SPECIFICATIONS

16728-Spec- .Net app for uploading work order confirmations.

Purpose

Create a .Net Application to generate a file to update the work order confirmations.

Admin Info

Purpose	.Net app for generating a file for work order confirmations
Requested By	Jeffrey Mau
Spec Created By	Venkat, Vamshi & Adithya
Spec Created Date	06/25/2015
Spec QA by	Venkat, Vamshi & Adithya
Objects	ZGET_SELECTION_POST ZNEC_PRE_MENU_ITM_CLICK ZNEE_EN008_IE_WODWLD_1 ZWO_PO_LINE
Document Status	Complete

Estimates

Sl.No	Activity	Estimation in Hours
1	Research	24
2	Documentation	12
3	Development/ Config	24
4	Unit test in DEV	16
5	Unit test in QUA	16
6	Other activity
	TOTAL	92

References

Prior Tickets

[Provide links of prior associated Spec / Break Fix BOSS document(s)]

Documents

[Attach any document(s) received for the requirement(s)]

Spec Changes

[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]

Sl.	Change Details	Requested By	Requested On	Notes if any

Functional Requirement

Purpose/WHY:

[Explain the purpose of the project and the reason why this requirement has come]
This functionality is being built to simplify the Work Order confirmations process in SNC for New Era's suppliers.
The standard SNC download/upload Excel spreadsheet functionality will be used to allow suppliers to confirm the WOs.

In Scope:

[List the activities to be included in scope]
Only Work Orders from open Purchase Orders will be allowed to be confirmed.

Out of Scope:

[Out of scope activities]

Solution Summary

[Discuss this section with Requester and get approval prior to beginning work]

Work Orders relating to Open POs will be downloaded into a CSV file via a daily job. (See Open issues for criteria)
This file will be sent to a .NET application where it will be loaded into a table with no changes. The table will always be truncated before loading the latest data.
Another file will be sent to .Net application where the file has the details like WO, PO & PO line. The naming convention of the
Users will use the .NET application to access the Work Orders for a selected PO. They will be shown rows that need to be confirmed (or have been confirmed previously)
Users will be allowed to confirm the remaining phases for any Work Order for that PO (in mass or individually)
At the end of the day, users will download the Work Order confirmations into a CSV file via an option on the .NET application.
Users will then upload the same file into SNC via a standard transaction
Security: Users will only be able to see their own company's POs.

Note: The following enhancements will be made to SNC-

Enhancement #1- A standard enhancement will be used to create a download file from SNC. This will automate the manual process. A standard enhancement already used by SAP for New Era will be modified for this purpose.
Enhancement #2 - A standard enhancement will be used to limit the data into the downloaded file. Only Work Orders for open POs will be downloaded.
Enhancement #3 - A link will be placed in SNC to allow users to access the .NET application

Test Plan

[List test scenarios/cases to be executed here]

Test ID	Test Scenario	Expected Results
SCM1	Full End to End Cycle with combination of two vendors.	End to End - Download & Upload must be done correctly.Validation Reports- Both CSV files created from SNC (WOs & POs) should contain ALL records per filter criteria (all WOs for open POs) Records loaded in .NET should contain ALL records received from SNC Confirmations in .NET should be reflected in SNC WO list. Confirmations in .NET should be reflected in ECC (via idoc)
SCM2	Execute scenarios with multiple upload/download cycles to ensure Work Orders statuses are updated correctly in SNC after each receipt from .NET	WO confirmations in SNC after each cycle should be correct. ECC idoc confirmations should be correct
SCM3	Download all upload only changed work orders	The File which generated for uploading confirmations must have the WOs which are updated with the confirmations. On Uploading the file the confirmations must be updated.
SCM4	Download the Wo with CNCL status and upload it and see if other work orders are updated with the status	The work orders other than the CNCL must be updated with confirmations
SCM5	Security check- User will try to enter PO which may or may not be part of their company	No EB POs Work Orders shall be seen in the ML Screen and vice versa
SCM6	Upload the file which has transport phase updated already but no COM status.	COM Shall be updated though Transport is updated with out deleting the existing updated in TRANSPORT
SCM7	Load Testing Upload Confirmations to Find Time
SCM8

.Net Application testing.

Test ID	Test Scenario	Expected Results
001	Enter PO number and click on Apply	The work order details for the PO will be displayed in the grid
002	Update the confirmations for the Phases by check and unchecking the checkboxes and save	User should be able to check and uncheck the checkboxes for the phase completed and the data should be saved to database on Save click
003	Day End Process	User should be able to download the updated confirmations.
004	Ensure all Open PO Lines Recieved

Download file Testing

Test ID	Test Scenario	Expected Results
DC001	Run the Download file Job 1. If any one line (WO) of a PO is active ( not updated with COM) 2. If No Work orders are updated with any phase of the PO. 3. If all work orders of the PO are updated with all Phases till COM 4. If Work orders of the PO lines are mix of Open, Closed & Complete	A file shall be placed in the application server. 1. All the work orders of that PO must be downloaded in the file. 2. All the work orders of that PO must be downloaded in the file. 3. No Work orders of that PO must be downloaded in the file. 4. All the work orders of that PO must be downloaded in the file.
DC002	Download the file wide open	All the Open POs and its corresponding Work orders must be downloaded in the file

Solution Details

[Provide complete technical details for configuration or programming here]
Here is the process:

Step 1: Generate the Active PO File from .Net Application
File 1:

Generate the selected Active PO's in .Net Application.
An FTP Script will be developed to place the Active PO File in SNC Application Server.
This will be run at end of the Day.

Step 2: Generate the Download file form Download Center
File 2:

Generate the Download File Daily with Work Orders for POs(File 1) and additional selection criteria as defined.
A Download Profile will be created and scheduled on daily execution.
Place File in Application Server

Filtration for the Downloaded file: (For more details please see Place File in Application Server)

The Downloaded file ignores all those Pos which are Closed.
Closed POs are termed as all the WOs of that PO are updated with all Phases, open POs are if any WO of that PO is open (left with any of the Phase Confirmation)

File Path in Application Server:
SND: /usr/sap/SND/WorkOrders
SNQ: /usr/sap/SNQ/WorkOrders
SNP: /usr/sap/SNP/WorkOrders

File 3:

This file shall contain Work Order Number ,PO number, PO Line item,Requested Delivery Date, Vendor Number, No Of Schedule Lines in PO Line in a .CSV file.
SCM - Adithya-Karthik - 2015-06-25 - 16728 - SNC-Program to send a WO_PO_LINE file to .Net application
The naming of the file will start with "WO_PO_LINE"

Step 3: Send the Download file to .Net Application

An FTP script will be developed to send the download file (from Download Center) to .Net Application

Step 4: Import the file to database using SSIS package

.NET SSIS packages will be developed to import the data from the files to the database.

Step 5:Update the confirmations for the .Net application

A .NET application will be created which can be called from the SNC UI.
The .NET Screen should contain PO number, PO line, Work Order, Phase ID, Product and Confirmation Check Box with filter functionality.
The .NET Screen should make the same look and feel of the Work Order work list screen.

Net - Vamshi -2015-07-01 - 16728.1100 - Spec -Supply Chain integration for Sourcing

Step 6: Download the Confirmations file form .Net Application

Download the file from .Net Application which includes only those Work Orders which are changed/modified (updated with confirmations)

Step 7: Upload the Confirmations file in the upload center

Upload the confirmations file in the Upload center and

Technical Details - ABAP
Link to .Net Application from SNC
Users can navigate from SNC to .Net Application by clicking Simple WO List in Reports section.

Create Root Node ROOT14_009 in Menu Path using transaction /SCF/UNAVCFG.
Maintain .Net Application URL in table "ZNEC_CRYSTL_PATH " for the above Root Node
Assign the root node to reports Menu Path by retreiving the URL from above table using Pre Exit "ZNEC_PRE_MENU_ITM_CLICK" in method "ONACTIONMAINMENU_ITEM_CLICK" and web dynpro component /SCF/UIWD.

Place File in Application Server

Save File in Application Server.
- Modify BADI "ZNEE_EN008_IE_WODWLD_1" to store the file which is downloaded in the application server.An Application server Path has to be created to store this file. The application server path is maintained in TVARVC table with field name as "ZWORKORDER_FILE" which will be used to place the file.
- File Name will start with CUST_NEC_WOACT_CONFIRMATION_TIMESTAMP (Eg: 201571215420)
Filter Data to reduce the size of file.
- To reduce the file size when download is run wide open, use Implicit Enhancement "ZGET_SELECTION_POST" in class /SCA/CL_FTR_DL_PROFILE.
  - Identify open Work Orders from tables
  - Get the PO's for the above Work Orders
  - Get all the Work orders for PO's from above step
  - Add the Work Orders to selection profile

Note:
Only those Work orders and Purchase Orders are seen in the .Net Application which are sent to the .Net in the downloaded file.

Issues

[List Issues / Bugs identified in configuration or development]